From: Ray Strode <rstrode@redhat.com>
Date: Tue, 5 Mar 2013 20:39:29 +0000 (-0500)
Subject: background: don't use raise_top() since it's costly
X-Git-Tag: archive/raspbian/50.5-1+rpi1~1^2~1013^2^2~4537
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/%22/%22http:/www.example.com/cgi/%22?a=commitdiff_plain;h=020128b9ca801f87f158e921f14f0ae585334008;p=gnome-shell.git

background: don't use raise_top() since it's costly

We currently resync the stacking order of the two key frames
every iteration of the animation.  This is costly and unnecessary.

This commit ensures they're stacked properly up front and doesn't
touch them after that.

https://bugzilla.gnome.org/show_bug.cgi?id=694993
---

diff --git a/js/ui/background.js b/js/ui/background.js
index 74e398eb3..6d6089b5c 100644
--- a/js/ui/background.js
+++ b/js/ui/background.js
@@ -356,7 +356,7 @@ const Background = new Lang.Class({
 
         let actor = new Meta.BackgroundActor();
         actor.content = content;
-        this.actor.add_child(actor);
+        this.actor.insert_child_at_index(actor, index);
 
         this._images[index] = actor;
         this._watchCacheFile(filename);
@@ -372,10 +372,8 @@ const Background = new Lang.Class({
     },
 
     _updateAnimationProgress: function() {
-        if (this._images[1]) {
-            this._images[1].raise_top();
+        if (this._images[1])
             this._images[1].opacity = this._animation.transitionProgress * 255;
-        }
 
         this._queueAnimationUpdate();
     },